@jacob-briscoe - thank you, makes sense, fixed.
BTW, I updated GHA versions as well.
Vitaly

Came to find this, thanks for taking the initiative and getting it done.

Can we get this merged, @ebinmore ? This is a really useful action!

Anyone?

This looks good and is a simple update that follows GitHub recommendations. It should be merged soon since GitHub has announced the deprecated functionality will be disabled soon.

Can we get this merged please? 😄

Thanks for getting this started! We use this action in many of our workflows, and getting it updated will be useful for us.

Taking a quick look at the PR, it looks like there's both a yarn.lock file and a package-lock.json file. On the current main branch, there's only a yarn.lock. It seems that the package-lock.json is extraneous, and can be safely removed.

Should we wait for this or the message is clear and this repo is abandoned?

Should we wait for this or the message is clear and this repo is abandoned?

@csaba-kovacs I'm confused about your comment. Is this repo supposed to be abandoned?

Edit: Oh I see what you meant... 4 months without response, I didn't see it was open for so long.

@ebinmore set-output will soon be deprecated in GitHub Actions. If you have access to the repository here, could you please merge it?

Should we wait for this or the message is clear and this repo is abandoned?

@csaba-kovacs I'm confused about your comment. Is this repo supposed to be abandoned?

Edit: Oh I see what you meant... 4 months without response, I didn't see it was open for so long.
@alexandre-perrin
#69 (comment)

This repo is abandoned: #69 (comment)

Anyone here will to establish themselves as the primary fork moving forward?

@aldenquimby I can't commit to any further maintenance, but I applied the changes in this PR to my forked branch and published it here: https://github.com/marketplace/actions/gha-slack-notify-build

Hi @vitalykarasik, is there any published version with recent changes in which you have upgraded the node version? If so, can you kindly share the link or the action name that I should use?

@justinr636 Can you also copy the changes and publish a latest version in this action? We are getting deprecation notice for node v16

Hi @vitalykarasik, is there any published version with recent changes in which you have upgraded the node version? If so, can you kindly share the link or the action name that I should use?

@MohamedAsan
My fork is now open, but I suggest not using it because we'll make it private soon.

You can use mine. I did the upgrade.

@csaba-kovacs Awesome, thanks a lot 💪